All committers have signed the CLA.

I had wanted something similar and made a note to myself:

We should expose a tool for semantic grepping with the ability to target contract/ function names, filter by visibility/purity,
Proposed CLI:

slither grep contracts/ [--contract|--function] [--pure,--nonpure] [--external-calls] [--unchecked] [--assembly]

I think that this is a decent start but I would imagine showing the source and line info so that it can be quickly examined or jumped to in the editor would be better. Wdyt?

Some time passed from this PR but I remember that choosing exact Contract.sol as target to query is preferable over iterating the whole directory - avoids information overload in the cli output.

So you won't need this part of the command:

...contracts/ [--contract|--function]... just Contract.sol

Current version was designed as query contract to find function. It's an interesting direction to also allow some grepping at the level of Function itself (has_require, has_loop, etc.).

I noticed you also included --unchecked and --assembly, I would also add --low_lvl_calls.

I also agree on adding one more string input flag to allow to find a specific function by full_name.

Showing source code of a Function is trickier UX-wise. Some functions will be long and cli output will get cluttered. Hence why I resorted to displaying structured info (it tends to be more or less the same length). Displaying a line reference is a great idea, most IDEs will just allow to jump automatically and we could avoid displaying source code in terminal.

To have a full grep like tool we could allow to actually grep the function's source code without cluttering the cli though!

slither grep Contract.sol --match 'try:' - that would find all functions using try/catch block ("try:" string) in the function source code.

I can ofc bring this PR home.

Also, wouldn't it be cool to have it as PythonAPI? This is how I actually implemented it for my own use, as an external class taking a list of Function to filter, returning Function(s) matching. I needed to resort to writing an external query class because there's no API (and this PR also doesn't propose it in the current state)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Added lines reference to the output (allows to Jump-to-line)

Added more filters:

--contains-asm (bool)
--low-lvl-calls (bool)
--full-name (str)
--in-source (str)

full-name allows user to search inside the function.full_name string (not an exact match)

in-source will search inside of the functions source code (not an exact match)

I think that covers most immediate needs we've seen mentioned by developers?

PS. It works best with the crytic-compile patch that's already merged but not yet released. If crytic.config.json is present in the working directory, it guarantees compilation and filtering.